Thanks for doing the UI work.

I don't have anything against this change, but I want to explore the topic of trigger techs a bit further:

For me the big challenge was to include the triggers into the tech tree / milestone analysis. Unfortunately it doesn't build up one big graph and then "simply" walks along edges and marks nodes as "available". It has some really weird logic. So I went the easy way, basically enabled all techs (by binding SpecialNames.TechnologyTrigger to the character) and hoped that the rest of the tech tree simply contains enough information for everything else to work. For vanilla that was OK, but the mods we need a better long-term solution.

e.g. the MineEntityTechnologyTrigger trigger needs a lot of requirements:

• if entity is non-resources entity (I guess this works, but I haven't checked): character needs access to a surface/planet where that entity can auto-spawn, or player is able to build one itself
• if entity is resource:
  • character needs access to a surface/planet where that resource can auto-spawn
  • character can mine its category or has access to a mining drill that can, and access to fuel for that drill, and the drill is allowed on that same surface/planet where the resource is
  • we need to respect MiningWithFluidModifier, which we don't support at all yet

To sum it up, I'm not surprised that the mine-entity trigger didn't work for you out of the box - and we need to think about how much brainpower we put into the trigger techs and how we prioritize it.

is it possible to also remove the ingredients that show up the "normal way"

I removed the 'recipe part' of the card when showing a research trigger technology, as all of the recipe details did not make much sense for the them:

@SWeini we could add another field to the Technology class instead of (ab)using the RecipeOrTechnology.ingredients field... This might prevent unforeseen/future issues...? 🤔

Rebased on fresh master